Financial Close Release PV9.0.0 SV201

The theme for this Hotfix release is bug fixes to Journal Entry Manager.

Highlights

  • We have streamlined functionality in Journal Entry Manager to improve your experience.

Fixed Issues

Journal Entry Manager

  • You can open journals and view all journal line items in read-only mode using the Manage option in Journal Entry Manager. (MP1-8262)

Upgrade Information

  • Review the information in this section before you install, deploy, or upgrade. OneStream strongly recommends that you upgrade in a Development environment before upgrading in the Production application.

  • Significant column, table names and template changes were made in the OFC PV8.4.0 SV100 release. Reference the release notes for more information, especially if you have customizations in place.

  • Uninstall UI prior to upgrading due to the migration to the OneStream Financial Close workspace.

  • The minimum version for upgrading OneStream Financial Close is OFC PV7.1.0 SV204. To download OFC PV7.1.0 SV204, please Contact Support.

  • Users with multiple instances will need to use the same instance number build of the current release when upgrading.

Compatibility

Component

Description

OneStream 9.0.0 or later

Minimum OneStream Platform release required to install this release of OneStream Financial Close.

See the Upgrade Guide.
Microsoft SQL Server

One of these versions of Microsoft SQL Server is required:

  • Standard Edition 2016 SP1 or later

  • Enterprise Edition 2012 or later

Documentation

  • Only the Release Notes were updated for this release. The Financial Close Guide has not been updated, except to change the release number and copyright if needed.

Contact Support

Contact OneStream Support by registering at:

Support - OneStream Software

Financial Close Release PV9.0.0 SV200

The theme for this Minor release is Transaction Matching Volume, Journal Entry Manager, and AI Anomaly Detection.

Highlights

  • Transaction Matching improves efficiency with the new All Status option for viewing and exporting transactions, rule copying across types, and rule extraction for easier testing and migration. You can now edit Match Rules after use, and Rule Instancing in the new Rule tab provides visibility into applied rule versions.

  • Journal Entry Manager streamlines processing with Recurring Journal Definitions to automate entries and Reversing Journals for quick reversals using prepopulated fields. Enhancements include viewing prior periods, attaching Excel files, honoring formulas during import, making Line-Item Fields optional, and overriding accounting period status.

  • AI in Account Reconciliations has been added, improving a variety of reconciliation processes that deliver comprehensive results.

New Features

Account Reconciliations

AI Anomaly Detection

  • Preparers and above can execute multiple Anomaly Detection jobs simultaneously, provided that each job operates on separate reconciliations. (MP1-7246)

  • From the Analysis and Reporting page, you can access the Anomaly Summary, which details the reconciliations you have access to and anomaly data, which includes multiple detector names. (MP1-7182, MP1-7630)

  • You can select single or multiple reconciliations and click AI Insights to run anomaly detection. If an anomaly gets automatically resolved the status will change from Unresolved to Auto-resolved. (MP1-7107)

  • After Anomaly Detection is initiated, you can view the identified anomalies and relevant information on the Anomalies tab in the Reconciliation Workspace. (MP1-6666)

  • The AI Settings page enables you to configure your Anomaly Detectors and Data Rules for Anomaly Detection. (MP1-6658)

  • Use the AI Insights button in the Reconciliations Grid to detect irregularities and the Anomalies tab in the Reconciliations Workspace to view the specific rule that triggered the anomaly. (MP1-6657)

  • You can address anomalies before certification by enabling the Critical Anomaly Resolution Required setting. You can also perform Mass Actions in the Reconciliations Grid with the Critical Anomaly Resolution Required setting. (MP1-7157, MP1-7109, MP1-7108, MP1-7907)

  • Anomaly Detectors display on the Anomaly Summary and Anomaly Trends pages. (MP1-8144)

  • OneStream Administrators and Solution Administrators can use the Delete button to delete anomalies. (MP1-7944)

  • OneStream Administrators and Solution Administrators can limit the view of anomalies to only internal users, preventing Auditors from viewing fully approved reconciliations. (MP1-7868)

  • Rule description has been added to the certification dialog box. (MP1-7677)

  • Preparers and Approvers can resolve critical anomalies when enabled. The setting in Certifications can only be configured by OS Admins and Solution Admins. (MP1-7676)

  • You can view and analyze anomalies on the Anomaly Trends dashboard. (MP1-7674)

Transaction Matching

  • You can use the (All Status) option in Transaction Matching to view and export all transactions regardless of status. (MP1-7781)

  • You can copy rules across different rule types in Transaction Matching to streamline rule creation. (MP1-7796)

  • You can extract rules from Transaction Matching and reimport them into a different application to simplify testing and migration. (MP1-7826)

  • You can edit Match Rules after they have been used in a match to maintain your application more efficiently. (MP1-7873)

  • You can use Rule Instancing to view the version of the rule applied to a match in the new Rule tab on the Match View page. (MP1-7877)

See What's New in Transaction Matching (2:29).

Journal Entry Manager

  • Recurring Journal Definitions streamlines the monthly closing process by automating journal entries that repeat over a defined range of accounting periods. (MP1-7136)

  • Reversing Journals enables you to quickly create a reversal of an existing journal by using the new Reverse icon, which prepopulates header fields, flips debit and credit amounts, and appends “_Reversal” to the journal name for efficient processing. (MP1-6965)

  • The Accounting Period dropdown now displays all prior closed periods in addition to current, open, and future periods, making it easier to locate and review historical journals.(MP1-7231)

  • Attach Excel import files to journals when enabled on the template, making it easier to reference the original import file. (MP1-7661)

  • When an import file contains calculated fields, formulas are honored and the resulting values are imported into Journal Entry Manager (MP1-7662)

  • You can override the accounting period status to reopen closed periods or close open periods for last-minute adjustments, with the option to reset to the auto-state when needed.(MP1-7698)

  • Line-Item Fields are now optional, giving administrators flexibility when creating templates and simplifying journal entry creation. (MP1-7824)

  • When a journal is rejected or unapproved, its extract is automatically deleted to prevent duplicate sends. (MP1-7903)

See What's New in Journal Entry Manager (3:55)

Fixed Issues

Account Reconciliations

  • Process should prevent actions that could cause the ProcessRecons job to fail due to a concurrency violation when running a custom Process data management job that includes the standard ProcessRecons step. (MP1-7278)

  • Discover failed to retrieve attributes for the next period when an account was deleted in the current period (for example the reconciliation existed in the next period but not the current period). (MP1-7360)

  • With Local Admin rights you can save changes made in the Access dialog on the Inventory and Group pages. (MP1-8213)

Transaction Matching

  • When viewing transactions with the Unmatched (As of Period End) status in Transaction Matching, the filtered results display only transactions from the current period. (MP1-7946)

  • You can export DS2 only from the Match screen in Transaction Matching, and the export includes all DS2 details as expected. (MP1-8081)

  • You can load a Shared Sources Fixed file to a larger match set without errors in Transaction Matching. (MP1-7912)

Upgrade Information

  • Review the information in this section before you install, deploy, or upgrade. OneStream strongly recommends that you upgrade in a Development environment before upgrading in the Production application.

  • Significant column, table names and template changes were made in the OFC PV8.4.0 SV100 release. Reference the release notes for more information, especially if you have customizations in place.

  • Uninstall UI prior to upgrading due to the migration to the OneStream Financial Close workspace.

  • The minimum version for upgrading OneStream Financial Close is OFC PV7.1.0 SV204. To download OFC PV7.1.0 SV204, please Contact Support.

  • Users with multiple instances will need to use the same instance number build of the current release when upgrading.

Compatibility

Component

Description

OneStream 9.0.0 or later

Minimum OneStream Platform release required to install this release of OneStream Financial Close.

See the Upgrade Guide.
Microsoft SQL Server

One of these versions of Microsoft SQL Server is required:

  • Standard Edition 2016 SP1 or later

  • Enterprise Edition 2012 or later

Documentation

  • The Financial Close Guide was updated to reflect these changes:

    • Release number

    • Rule Instancing and other enhancements in Transaction Matching.

    • Recurring Journals Definitions and other enhancements in Journal Entry Manager.

    • Anomaly Detection in Account Reconciliations.

Known Issues

Account Reconciliations

  • For Platform Versions 8.5.0 to 9.0.0, in the Filter Editor, when you view a filter that contains groups, a Parser error displays. (PF1-11222)

  • For Platform Versions 8.5.0 to 9.0.0, when you select the Apply button, existing filter criteria display in the Filter Results grid but not in the Filter Editor. (PF1-11221)

Transaction Matching

  • A Database Insert Error displays when updating the TXM Rules or Reason Codes tables.(MP1-7489)

  • If you use multiple instances of OFC with Indexing in TXM, you'll encounter errors. These will be resolved in version OFC PV9.0.0 SV200. If you need assistance, please contact Support. (MP1-7926)

Contact Support

Contact OneStream Support by registering at:

Support - OneStream Software

Financial Close Release PV9.0.0 SV101

The theme for this Hotfix release is bug fixes to Transaction Matching and Account Reconciliations.

Highlights

  • We have streamlined functionality in Transaction Matching and Account Reconciliations to improve your experience.

Fixed Issues

Transaction Matching

  • With cube and dataset security enabled, you can open the Dashboard and Analysis page with transactions statistics adhering to configured security settings. (MP1-8200)

  • When cube and dataset security is enabled with Entity selected, Matched transactions created by rules unmatch. (MP1-8218)

Account Reconciliations

  • With Local Admin rights you can save changes made in the Access dialog on the Inventory and Group pages. (MP1-8210)

Upgrade Information

  • Review the information in this section before you install, deploy, or upgrade. OneStream strongly recommends that you upgrade in a Development environment before upgrading in the Production application.

  • Significant column, table names and template changes were made in the OFC PV8.4.0 SV100 release. Reference the release notes for more information, especially if you have customizations in place.

  • Uninstall UI prior to upgrading due to the migration to the OneStream Financial Close workspace.

  • The minimum version for upgrading OneStream Financial Close is OFC PV7.1.0 SV204. To download OFC PV7.1.0 SV204, please Contact Support.

  • Users with multiple instances will need to use the same instance number build of the current release when upgrading.

Compatibility

Component

Description

OneStream 9.0.0 or later

Minimum OneStream Platform release required to install this release of OneStream Financial Close.

See the Upgrade Guide.
Microsoft SQL Server

One of these versions of Microsoft SQL Server is required:

  • Standard Edition 2016 SP1 or later

  • Enterprise Edition 2012 or later

Documentation

  • Only the Release Notes were updated for this release. The Financial Close Guide has not been updated, except to change the release number and copyright if needed.

Contact Support

Contact OneStream Support by registering at:

Support - OneStream Software

Financial Close Release PV9.0.0 SV100

The theme for this Major release is Dynamic Attribute Mapping (DAM) in Account Reconciliations, Transaction Matching Volume, Purging, and Archiving, and the initial release of Journal Entry Manager (JEM).

Highlights

  • Dynamic Attribute Mapping automates the maintenance of reconciliation attributes. You can set risk assignments, balance thresholds, and more using rule-based logic and scheduled tasks, making it more efficient to run the reconciliation process.

  • Transaction Matching Archiving enables you to maintain matched transactions in the system by compressing the matched transactions to reduce database storage, while Transaction Matching Purging permanently deletes the matched transactions, streamlining the processing of large transaction volumes.

  • Journal Entry Manager (JEM) is a centralized, finance-owned solution within OneStream that streamlines journal entry management across ERP systems.

Watch a Dynamic Attribute Mapping Overview (4:23).

New Features

Account Reconciliations

Dynamic Attribute Mapping

  • You can access the Dynamic Attribute Mapping Rules page under the Administration tab tocreate, copy, edit, delete, or run rules. (MP1-6501, MP1-6502, MP1-6503, MP1-6504)

  • Construct your filter criteria during rule creation by using the Filter Editor. (MP1-6500, MP1-6506)

  • You can define attributes during the rule creation process on the Set Reconciliations page.(MP1-6505)

  • Preview active and inactive rules that passed validation and are eligible for updates in the Proposed Updates grid. (MP1-6854)

  • Run a rule to update attributes to a selected rule. Active rules will run in the order specified and at the scheduled start period. (MP1-6885, MP1-6886)

  • Actions that are blocked during process are blocked during the execution of run. If a blocked action is performed during execution, an error message displays. (MP1-6770)

  • The Audit Log contains a Rule column enabling you to identify the rule responsible for an attribute update during reconciliation. (MP1-6508, MP1-6887)

Transaction Matching

  • You can use Task Scheduler to schedule Archiving and Purging jobs. (MP1-7759)

  • Transaction Matching Administrators can set Archive and Purge retention days at the match set level the Data Retention page to Archive and Purge transactions based on the match date.(MP1-7757, MP1-7742, MP1-7577)

  • Account Reconciliations can retrieve archived, linked matches from Transaction Matching.(MP1-7584)

  • You can create custom filters in Transaction Matching. (MP1-7578)

  • You can view table details and manage indexes on the Index Administration page in Transaction Matching. (MP1-7506)

  • The Table Editor has been updated with Dynamic Grids on Transactions Grid and Detail Items Dashboards. (MP1-7505)

  • Transaction Matching can scale up to 200 million ingested transactions per month with appropriate match and reporting functionality. (MP1-7467)

Fixed Issues

Account Reconciliations

  • You can download the audit file for a multicurrency reconciliation. (MP1-7233)

  • You can delete an R-Doc attached to an individual reconciliation through the Reconciliation page after it is assigned to an account group. (MP1-7189)

  • When the reconciliations currency is set to (Local), the balance is translated. (MP1-7282)

  • If the group status is Balance Changed, only the child items with a balance change will show the status of Balance Changed. Child items without a balance change will have a status of In Process. (MP1-7913, MP1-7915)

Transaction Matching

  • No Object Reference error occurs when you access the Transactions page prior to configuring Data Sets. (MP1-7488)

  • Transactions and Matches export open an excel spreadsheet displaying transactions data according to the Export Type selection. (MP1-7480, MP1-7473)

  • You can push Detail Items to Account Reconciliations when status filter is set to Matched.(MP1-7477)

  • No error displays when setting the Reason Code to Unassigned in the Edit Transactions window. (MP1-7476)

  • Inactive Reason Codes do not display in the Match Reason Code drop-down menu. (MP1-7475)

  • You can filter Transactions by Match Reason Code and edit Transactions in Dynamic Grid without receiving an error. (MP1-7470, MP1-7879)

Upgrade Information

  • Review the information in this section before you install, deploy, or upgrade. OneStream strongly recommends that you upgrade in a Development environment before upgrading in the Production application.

  • Significant column, table names and template changes were made in the OFC PV8.4.0 SV100 release. Reference the release notes for more information, especially if you have customizations in place.

  • Uninstall UI prior to upgrading due to the migration to the OneStream Financial Close workspace.

  • The minimum version for upgrading OneStream Financial Close is OFC PV7.1.0 SV204. To download OFC PV7.1.0 SV204, please Contact Support.

  • Users with multiple instances will need to use the same instance number build of the current release when upgrading.

Compatibility

Component

Description

OneStream 9.0.0 or later

Minimum OneStream Platform release required to install this release of OneStream Financial Close.

See the Upgrade Guide.
Microsoft SQL Server

One of these versions of Microsoft SQL Server is required:

  • Standard Edition 2016 SP1 or later

  • Enterprise Edition 2012 or later

Documentation

  • The Financial Close Guide was updated to reflect these changes:

    • Release number

    • Dynamic Attribute Mapping functionality in Account Reconciliations

    • Custom Service Factory customization in Transaction Matching

    • New section for Journal Entry Manager (JEM) solution included in the guide

  • The solution Help icon now prompts a dialog where you can access online help documentation. (MP1-7762, MP1-7783, MP1-7919, MP1-7920)

Known Issues

Account Reconciliations

  • For Platform Versions 8.5.0 to 9.0.0, in the Filter Editor, when you view a filter that contains groups, a Parser error displays. (PF1-11222)

  • For Platform Versions 8.5.0 to 9.0.0, when you select the Apply button, existing filter criteria display in the Filter Results grid but not in the Filter Editor. (PF1-11221)

Transaction Matching

  • A Database Insert Error displays when updating the TXM Rules or Reason Codes tables.(MP1-7489)

  • If you use multiple instances of OFC with Indexing in TXM, you'll encounter errors. These will be resolved in version OFC PV9.0.0 SV200. If you need assistance, please contact Support. (MP1-7926)

Contact Support

Contact OneStream Support by registering at:

Support - OneStream Software